Remove the OSTREE_MAX_RECURSION limit on metadata depth
authorBrian C. Lane <bcl@redhat.com>
Fri, 2 Jun 2017 15:30:43 +0000 (08:30 -0700)
committerAtomic Bot <atomic-devel@projectatomic.io>
Fri, 2 Jun 2017 16:18:28 +0000 (16:18 +0000)
commitc651982929ec142d107e87d9f32ca324dffd4772
tree4c041e01468d78603e382eba427b4586d4bf126a
parentcad42d960150db19bfaa518a06cea1febeb8fb58
Remove the OSTREE_MAX_RECURSION limit on metadata depth

This was making it impossible to pull or mirror a large ostree repo, and
according to Colin is no longer necessary. It works fine with a test
against a repo with 2741 commit and 451468 objects in it.

Closes: #899
Closes: #904
Approved by: jlebon
apidoc/ostree-sections.txt
src/libostree/ostree-core.h
src/libostree/ostree-repo-pull.c